You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🛑 The pull request has been removed from the queue default
Pull request #4233 has been dequeued due to failing checks or checks timeout.
You can take a look at Queue: Embarked in merge queue check runs for more details.
In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment @mergifyio refresh on the pull request.
🛑 The pull request has been removed from the queue default
The queue conditions cannot be satisfied due to failing checks.
You can take a look at Queue: Embarked in merge queue check runs for more details.
In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment @mergifyio refresh on the pull request.
Nov 9 12:43:03.487: INFO: Waiting for PV pvc-df79f100-e412-408e-af7a-b8e3c8d443cf to bind to PVC rbd-pvc
Nov 9 12:43:03.487: INFO: Waiting up to timeout=10m0s for PersistentVolumeClaims [rbd-pvc] to have phase Bound
Nov 9 12:43:03.489: INFO: PersistentVolumeClaim rbd-pvc found and phase=Bound (1.875492ms)
Nov 9 12:43:03.489: INFO: Waiting up to 10m0s for PersistentVolume pvc-df79f100-e412-408e-af7a-b8e3c8d443cf to have phase Bound
Nov 9 12:43:03.491: INFO: PersistentVolume pvc-df79f100-e412-408e-af7a-b8e3c8d443cf found and phase=Bound (1.794611ms)
W1109 12:43:03.499504 91009 warnings.go:70] would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "web-server" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "web-server" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "web-server" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "web-server" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
Nov 9 12:43:03.499: INFO: Waiting up to csi-rbd-demo-pod to be in Running state
Nov 9 12:53:03.500: INFO: failed to write data in the pod: context deadline exceeded
Nov 9 12:53:03.500: INFO: >>> kubeConfig: /root/.kube/config
�[38;5;9m[FAILED]�[0m in [It] - /go/src/github.com/ceph/ceph-csi/e2e/utils.go:1125 �[38;5;243m@ 11/09/23 12:53:03.507�[0m
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
nixpanic
force-pushed
the
add/allow-mkfsOptions-from-chart
branch
from
Describe what this PR does
mkfsOptionsparameter in the ceph-csi-rbd chart.Is there anything that requires special attention
Do you have any questions? False
Is the change backward compatible? True
Are there concerns around backward compatibility? False
Provide any external context for the change, if any.
For example:
Related issues
N/A
Future concerns
List items that are not part of the PR and do not impact it's
functionality, but are work items that can be taken up subsequently.
Checklist:
guidelines in the developer
guide.
Request
notes
updated with breaking and/or notable changes for the next major release.
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>: retest the<job-name>after unrelatedfailure (please report the failure too!)